Skip to content

2019-dec sec release post-announcement#2838

Merged
sam-github merged 7 commits intomasterfrom
december-2019-post-release
Dec 18, 2019
Merged

2019-dec sec release post-announcement#2838
sam-github merged 7 commits intomasterfrom
december-2019-post-release

Conversation

@sam-github
Copy link
Copy Markdown
Contributor

Note that vulnerability descriptions are verbatim from the npm vulnerability descriptions.

@sam-github sam-github force-pushed the december-2019-post-release branch from 3dcb49c to 37c02ae Compare December 18, 2019 00:46
@sam-github
Copy link
Copy Markdown
Contributor Author

@nodejs/tsc @nodejs/security

@sam-github sam-github force-pushed the december-2019-post-release branch from 37c02ae to 0abe334 Compare December 18, 2019 00:54
Copy link
Copy Markdown
Member

@Trott Trott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubber-stamp LGTM

Comment thread locale/en/blog/vulnerability/december-2019-security-releases.md Outdated
@sam-github sam-github force-pushed the december-2019-post-release branch from 0abe334 to 960b209 Compare December 18, 2019 01:27
Comment thread locale/en/blog/vulnerability/december-2019-security-releases.md Outdated
Comment thread locale/en/blog/vulnerability/december-2019-security-releases.md Outdated
Comment thread locale/en/blog/vulnerability/december-2019-security-releases.md Outdated
Comment thread locale/en/blog/vulnerability/december-2019-security-releases.md Outdated
Comment thread locale/en/blog/vulnerability/december-2019-security-releases.md Outdated
Comment thread locale/en/blog/vulnerability/december-2019-security-releases.md Outdated
Copy link
Copy Markdown
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

sam-github and others added 6 commits December 17, 2019 17:47
@sam-github sam-github merged commit 16e12ef into master Dec 18, 2019
@sam-github sam-github deleted the december-2019-post-release branch December 18, 2019 02:03

### Arbitrary File Write

Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended `node_modules` folder through the `bin` field. A properly constructed entry in the package.json `bin` field would allow a package publisher to modify and/or gain access to arbitrary files on a user’s system when the package is installed. It is only possible to affect files that the user running `npm install` has access to.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A slight clarification: It is not possibly to overwrite files or modify files. You are only able to places files in locations that already do not exist. It is not possible to "gain access to arbitrary files" this is all about writing.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@evilpacket This is verbatim copied from the npm vulnerability report, the link to which is provided a few lines down. Please provide this feedback to npm, inc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants